This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
I can explain the TCP/HTTP on the server status, but that wasn't the real problem.
To maintain backwards compatibility with pre-8.5.2 clients (that only did TCP or SMS push), the default notification type is TCP. When the device connects to the server the first time, it will get set to TCP. Whenever the device actually connects to push, the notification type will be updated to whatever is really in use (TCP or HTTP). Thus, it said TCP because the client had yet to successfully connect via HTTP. As soon as it connected via HTTP, it was uploaded successfully.
The notification type of TCP or HTTP doesn't really matter (it is mainly informational) as the server can send the message using whatever connection the device has open to the server at the time. Therefore, this wasn't causing the real problem - it was just an indication that push wasn't connecting.
Therefore, something in the networking changes you made on the device finally allowed push to connect (over HTTP). Given that you changed the roaming setting, I suspected it might be related to the new 8.5.2 setting for roaming detection which doesn't allow Traveler to connect when roaming (by default - you can change how Traveler handles roaming in the Traveler settings). But that setting isn't in the Android client yet (it is for WM and Nokia), so then that cannot be it.
Thus, I suspect it was related to the device and roaming somehow, but I'm not sure exactly how.
If you run into it again (or you still have it), it would be great to get a TPR from when you had the problem. That would tell us if the roaming is involved or not. If not, it might show some other network error that would make sense.
Feedback response number RSSN8CUK4V created by ~Michelle Umapuloni on 01/06/2011
RE: Solution
Return to top
. . . . RE: Solution (~Manny Ekrevero... 6.Jan.11) 
